Single-block virtual frame buffer translated to multiple physical blocks for multi-block display refresh generator

ABSTRACT

A graphics controller for a System-On-a-Chip (SOC) used with a battery-powered device allows for reduced-power display modes. The microprocessor writes to a frame buffer that is a single, contiguous address block in virtual memory. A memory management unit (MMU) translates frame-buffer address to multiple physical blocks. The graphics controller fetches pixels from the multiple physical blocks, including a block in an on-chip memory and a block in an external memory. In a low-power mode, pixels are only fetched from the lower-power on-chip memory and not the higher-power external memory. A smaller display window is defined and pixels outside the window are replaced by dummy data, .eliminating external-memory fetches. The smaller display window falls within the first block in the on-chip memory. Status and other information can be displayed in the smaller display window during stand-by modes, while a full-screen of data is displayed for full-power modes.

BACKGROUND OF INVENTION

Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 6,680,738. The reissue applications are the present application, which is a broadening reissue of the '738 Patent, and application Ser. No. 12/789,856, which is a divisional broadening reissue of the '738 Patent.

This invention relates to computer-graphics systems, and more particularly to frame buffers split among multiple blocks in memory.

An interesting variety of small consumer devices are appearing. Portable computing and/or communication devices such as the personal digital assistant (PDA), Pocket PC, and smart cellular phones have an astonishing computing power for such small devices. These portable, often hand-held, computing devices often use a very-large-scale-integration (VLSI) chip that includes a microprocessor or central processing unit (CPU), memory, and I/O controllers on a single silicon chip known as a System-On-a-Chip (SOC).

These consumer devices run on battery power to achieve portability. The battery must be made small and light to keep the size and weight of the overall device small. Such small batteries necessitate the use of low-power chips including the SOC.

The SOC can include an on-chip static random-access memory (SRAM). Program running on the SOC's CPU can access data from an on-chip read-only-memory (ROM) and write data to the on-chip SRAM. Using the on-chip SRAM reduces power, since this avoids access cycles to an external dynamic-random-access memory (DRAM) that require more power to drive the larger off-chip capacitances.

Some accesses of the external DRAM may still be needed to load a very large program into the SRAM, or to fetch very large data files. Once these are stored and fetched, the external DRAM can be powered down while the program and frame buffer are located and executed within the on-chip SRAM. Use of the on-chip SRAM also improves performance, as SRAM access times are faster than access times to the external DRAM.

The SOC may include a graphics controller that continuously reads pixel data from a frame buffer and sends these pixels off-chip from the SOC to a display. The display can be a small liquid crystal display (LCD) that requires little power, or other compact display. The frame buffer can be a portion of the on-chip SRAM that is written by the CPU when updating the display. Using the internal SRAM for the frame buffer can further save power, since external accesses of an external frame-buffer memory are avoided.

However, larger, more colorful displays running at higher-resolution modes may require a large frame buffer to store a large number of pixels. Higher-color modes require more storage bits per pixel, and higher resolutions have more pixels to store. The on-chip SRAM may need to be enlarged to provide sufficient capacity for these larger frame buffers. However, larger on-chip SRAMs increase the SOC die size and reduce manufacturing yield. The SOC may even become too expensive for many low-cost consumer devices.

For example, a display of 320×240 pixels having one byte per pixel requires 76,000 bytes, which fits in a 100 Kilo-Byte (KB) SRAM. However, a more colorful display using 16 bits per pixel requires about 150 KB, which is larger than the 100 KB SRAM.

The frame buffer could be split among the on-chip SRAM and the external DRAM. However, all software programs running on the CPU expect the frame buffer to be a single, continuous block of address. Re-writing the many programs that can run on the CPU to allow for a split frame buffer is not practical. Programs are written expecting a conventional frame buffer with a contiguous block of addresses.

What is desired is a SOC that supports a frame buffer that can be split among multiple blocks of memory in the internal SRAM and the external DRAM. A graphics controller that can re-assemble pixels from the multiple blocks is desirable. A SOC that has a high-power display mode that splits the frame buffer between the on-chip SRAM and the external DRAM, and with a low-power display mode that only uses the on-chip SRAM is desired. It is further desired that the frame buffer appear to be a single, contiguous block of memory to programs executing on the CPU.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a System-On-a-Chip (SOC) with a multi-block frame buffer.

FIG. 2 is a memory-map diagram showing CPU writes to the frame buffer.

FIG. 3 is a memory-map diagram showing display-refresh fetches from the multi-block frame buffer.

FIG. 4 shows page translation.

FIG. 5 is a diagram of refresh address generation for fetching frame-buffer pixels from multiple physical blocks.

FIG. 6 is a display-timing diagram showing a block ending in the middle of a display line.

FIG. 7 is a display-timing diagram showing a block ending after the end of a display line in the off-screen area.

FIG. 8A shows a display that is refreshed with pixels from the on-chip SRAM and from the external SDRAM.

FIG. 8B shows a reduced-size display mode that is refreshed with pixels from the on-chip SRAM.

DETAILED DESCRIPTION

The present invention relates to an improvement in frame buffers. The following description is presented to enable one of ordinary skill in the art to make and use the invention as provided in the context of a particular application and its requirements. Various modifications to the preferred embodiment will be apparent to those with skill in the art, and the general principles defined herein may be applied to other embodiments. Therefore, the present invention is not intended to be limited to the particular embodiments shown and described, but is to be accorded the widest scope consistent with the principles and novel features herein disclosed.

FIG. 1 is a block diagram of a System-On-a-Chip (SOC) with a multi-block frame buffer. SOC 10 is a single-chip system that communicates with external peripherals 26 and display 29. CPU 12 executes program instructions from ROM. 16 or from internal on-chip SRAM 22, or from external synchronous DRAM (SDRAM) 28 through external memory controller 20. Memory management unit (MMU) 14 translates logical addresses from CPU 10 into physical addresses. MMU 14 can perform memory-page swapping and other functions.

Peripherals 26 can include a keypad or pointing device that inputs commands or selections from a user. Peripherals 26 can include other devices, such as a speaker, light-emitting diode lights, cable connectors, etc. I/O controller 18 has registers that can be read and written by CPU 12 over internal bus 15 to communicate with and control peripherals 26. Timers, direct-memory access (DMA), or other I/O controller functions may be included in I/O controller 18.

Graphics display controller 24 drives a stream of pixels to external display 29 to refresh the display. These pixels are fetched from a frame buffer in on-chip SRAM 22 for low-power display modes when the entire frame buffer fits inside SRAM 22. However, for higher-resolution, higher-color, higher-power display modes the frame buffer does not completely fit in SRAM 22. Instead, the frame buffer is divided among two or more blocks. At least one block is in SRAM 22, but one or more other blocks are located in external SDRAM 28.

Graphics display controller 24 contains address-generation and boundary-checking logic to fetch some pixels from SRAM 22, while other pixels are fetched from SDRAM 28 using external memory controller 20.

Programs running on CPU 12 update the display by writing pixels to a single-block frame buffer in the logical address space. MMU 14 translates these memory accesses from CPU 12 into the physical addresses of multiple blocks in SRAM 22 and SDRAM 28. Thus programs see a frame buffer with a single memory block, but graphics display controller 24 sees a frame buffer with multiple memory blocks.

FIG. 2 is a memory-map diagram showing CPU writes to the frame buffer. Programs running on CPU 12 update the display by over-writing pixels in the frame buffer. These programs write pixels using virtual address within virtual address space 30. The frame buffer is a continuous block of virtual address that include virtual blocks 32, 34. The starting address and size of the frame buffer are set by the application program or operating system depending on the current graphics mode.

Memory writes from CPU 12 are sent to MMU 14 before actually being written to the frame-buffer memory. MMU 14 translates the virtual address from CPU 12 into a physical address for the memory. The physical address is within physical address space 40, which includes both on-chip addresses 90 in the on-chip SRAM, and external addresses 92 in the external SDRAM.

The frame buffer is split among two blocks in this example. Display block A is virtual block 32 in virtual address space 30, but physical block 42 in physical address space 40. Pixels to block 32 are translated by MMU to addresses within block 42 so that the pixels are written to on-chip SRAM.

Display block B is virtual block 34 in virtual address space 30, but physical block 44 in physical address space 40. Pixels to block 34 are translated by the MMU to addresses within block 44 so that the pixels are written to the external SDRAM. Thus although blocks 32, 34 are continuous in virtual address space 30 accessed by programs, pixels are stored in separate physical blocks 42, 44 in different physical memory devices.

FIG. 3 is a memory-map diagram showing display-refresh fetches from the multi-block frame buffer. Pixels are stored in multiple physical blocks 42, 44 in physical address space 40.

Graphics display controller 24 reads pixels from physical block 42 with internal addresses for the on-chip SRAM. These pixels are displayed as display block 46 on display 29. Graphics display controller 24 also reads pixels from physical block 44 with external addresses for the external SDRAM. These pixels are displayed as display block 48 on display 29. Thus Graphics display controller 24 reads separate physical-memory blocks and combines them into a single frame of display.

FIG. 4 shows page translation. The MMU contains one or more page-translation table 50. Table 50 contains translation entries such as logical, physical address pairs. Recently-used entries can be cached from a larger, more complete table.

Logical address 52 is generated by the CPU and contains a least-significant-bits (LSB) portion known as offset 56. The most-significant-bits (MSB) portion of logical address 52 is page base address 54, or simply the page address.

Page base address 54 of logical address 52 is used to lookup an entry in translation table 50. The entry for page base address 54 contains a translated page address, which is output from table 50 as translated page address 55.

Physical address 53 is formed by concatenating translated page address 55 with offset 56 from logical address 52, which is unchanged as offset 57. Offset 56, 57 can be considered the address within a page that is identified by page base address 54 in the logical address space, or translated page address 55 in the physical address space. In this example, offsets 56, 57 are 12 bits, for a page size of 4 KB.

FIG. 5 is a diagram of refresh address generation for fetching frame-buffer pixels from multiple physical blocks. Start address selector 60 selects the screen starting address, or the block start address. The screen starting address is the address location of the first pixel on the screen, usually the upper-left pixel of the top line. The block start address is the address of the first pixel in the next physical block of the display frame buffer. A hardware selector can be used to select the proper start address for start address selector 60, or a program or firmware can load the proper start address at the desired time.

Just before the start of a new screen, VS is activated, and the screen starting address from selector 60 is fed through mux 62 to line start register 64. Otherwise, mux 62 selects the next line starting address, LSA(n+1), when the vertical sync VS is not active. This allows the address for the next horizontal line of pixels to be generated.

The new screen address (SSA) selected by mux 62 can be loaded into line start register 64 when both HS and VS are active. Then, after the end of the horizontal sync (HS), the screen start address (SSA) in the line start register 64 is latched into memory address counter 66 at the end of the horizontal sync.

Memory address counter 66 is incremented by the pixel size for each pixel clock PCLK during the display time, when both horizontal display active HDA and vertical display active VDA are on. Memory address counter 66 is loaded with the line start address from line start register 64 before the beginning of each line towards the end of the HS timing after line start register 64 is loaded with a new value at the beginning of HS. Memory address counter 66 contains a physical address that is sent the physical memory to fetch the next pixel. The physical address is in the on-chip SRAM for the first block, but can be in the external SDRAM for other blocks of the frame buffer.

Adder 70 generates the next line's starting address, LSA (n+1), by adding the current line start address from line start register 64 to the screen-image width SIW from screen-width register 68. Screen-width register 68 contains the width of the screen, which is the number of pixels in the displayed line plus the number of pixels in the off-screen (non-displayed) part of the line, multiplied by the pixel width in bytes (or other addressable units of the physical memory). This next-line starting address is selected by mux 62 to be loaded into line start register 64 at the beginning of the next HS.

The physical address of the current pixel from memory address counter 66 is compared by detector 72 to the block end address BEA in register 76. When the current pixel's address matches the block end address, the end of the block has been reached. The next pixel must be fetched from a different physical block, which may not be contiguous with the current block.

Sometimes the block end may occur at the end of a line of pixels, or between the address at the end of a line and the next line's start address, rather than in the middle of the line. Then the block end is not detected by detector 72. Instead, comparator 74 detects that the next line's starting address (which is generated by adder 70) is greater than the block end address from BEA register 76.

When the end of the block is detected by either detector 72 (block ends in the middle of a line) or comparator 74 (block ends at end of line), block end signal BE is activated. The next-line address from adder 70 is no good as it over-runs or exceeds the end of the block. Instead, the start address of the next block is used. This block start address (BSA) is selected to be output from start address selector 60 prior to the end of the current block. Mux 62 selects the new block's start address from start address selector 60 when BE is activated. The new block start address is latched into line start register 64 by the BE signal during the vertical display active time VDA.

Memory address counter 66 is loaded with the new block start address from line start register 64. The next pixel in the line is fetched from the new physical memory block at this block starting address. Memory address counter 66 then continues to count up with the pixel clock, reading pixels from the new physical block. Adder 70 generates the next line's starting address, LSA(n+1) from the block's starting address in line start register 64. At the end of the line, when HS is activated, this new line's address is latched into line start register 64 through mux 62, and pixel fetching continues with the second display line in the new physical block.

The screen starting address in start address selector 60 is a full-width address. The full address can be loaded into both the upper (U) and lower (L) portions of line start register 64 and memory address counter 66 as described above. This allows the physical blocks to have an arbitrary length. However, the block start address uses a fixed block size, such as fixed-size pages. For example, the page size (length) is often set to 4K bytes, where the lower 12 address bits are the offset within the page. Then the page's (block's) starting address can be specified by just the upper m−12 address bits, where m is the address width in bits. For example, a 32-bit address can use just the upper 20 bits as the page starting address, since it is assumed that the lower address bits are all zero's for the first address in the page.

Using such fixed-length physical-memory blocks, or pages, is advantageous because smaller-width registers and logic paths can be used. Lower address bits can be quickly zeroed out when a new physical block is started. When a new block address is loaded from start address selector 60 through mux 62 to line start register 64, the upper bits are loaded from start address selector 60 by mux 62 into the upper portion of line start register 64. The lower bits are zeroed by mux 62 and loaded as zeros into the lower portion of line start register 64. Likewise, the lower portion of memory address counter 66 can become zero at the start of a new block, and just the upper bits loaded from line start register 64. If the block end occurs between the end of a line and the next start address, the lower portion of memory address counter 66 can be loaded from output of the adder 70 through mux 62 and line start register 64. This is not the start of a new block, so just the upper bits loaded from line start register 64.

Since all physical addresses within a block have the same upper address bits, the upper portions of line start register 64 and memory address counter 66 can continue to be loaded from start address selector 60 for each new line, if the next line start address is in the same block. Alternately, the upper portions can be loaded just once at the start of the block, and not re-loaded when the lower-portions are loaded for each new display line.

An overflow or carry-out signal from the lower portion of memory address counter 66 is an input to detector 72. If the block end address register 76 and upper portion of memory address counter 66 are equal, then the BE signal become active. Adder 70 outputs the next line's start memory address which is input to comparator 74 to compare with block end address register 76 to signal the block end BE when the next line's start address is greater than block end address register 76.

Block Ends in Middle of Display Line—FIG. 6

FIG. 6 is a display timing diagram showing a block ending in the middle of a display line. Just two physical blocks are shown for clarity, but more blocks could be used in an actual system. Pixels are written to the display from the upper left to the upper right in the first line (LSA0), and then for other lines from top to bottom.

The displayable area occurs for only a portion of the total frame time. Pixels are written to the display during the horizontal display active HDA time of a line, but not when HDA is off at the end of each line. The horizontal sync signal HS occurs when HDA is off at the ends of the lines.

Displayable lines of pixels are written to the display during the vertical display active VDA time, but not after the last line is written and VDA is turned off. Then the vertical sync VS signal occurs. Both the VS and HS signals are active near the end of the display frame timing.

The first physical block A, display block 46, begins with the screen starting address SSA at the beginning of line LSA0, and ends with BEA on line LSA(n). Block 46 ends in the middle of line LSA(n). Block-end signal BE is activated by the detector when the memory address counter matches the block-end address. Then the starting address of the next physical block is loaded into the line start register.

The first pixel in the second physical block B is read from the block start address BSA and written to the display to continue the current line LSA(n). Then other pixels in line LSA(n) in block 48 are written, and the next line LSA(n+1) in block 48 and subsequent lines are written.

Block Ends after End of Display Line in Off-Screen Area—FIG. 7

FIG. 7 is a display timing diagram showing a block ending after the end of a display line in the off-screen area. The first physical block A, display block 46, begins with the screen starting address SSA at the beginning of line LSA0, and ends with BEA in the off-screen portion of line LSA(n). Block 46 ends in the off-screen portion of line LSA(n), after HDA ends. The memory address can skip from the end of line N to LSA (N+1). There might be no actual memory accesses to the address BEA and BSA.

Block-end signal BE is activated by the comparator when the next-line starting address generated by the adder exceeds the block-end address. Then the upper portion (U), bits m−12, of the next-line address generated by adder 70 is discarded. Instead, the upper portion (U) of the starting address of the next physical block is loaded into the line start register from start address selector 60. The lower part (L), bits 11-0, generated by adder 70 is loaded to memory address counter 66 through mux 62 and line start address register 64.

The first pixel in the second physical block B is read and written using the address value from memory address counter 66. It is the first displayable pixel in the next line LSA(n+1). Then other pixels in line LSA(n+1) in block 48 are written, and subsequent lines are written.

Full-Power Mode Fetches Pixels from Both On-Chip and External Memories—FIG. 8A

FIG. 8A shows a display that is refreshed with pixels from the on-chip SRAM and from the external SDRAM. The first physical block A begins with the screen start address SSA and is a block in the on-chip SRAM. These memory accesses require less power since no off-chip signals are driven. Access times can be faster. First block 46 continues until the block end address BEA.

The second block B of the frame buffer begins at block start address BSA. Second block 48 continues to the end of the displayable area in this simplified example. This second block 48 is stored in external SDRAM, which requires more power to access than the on-chip SRAM since external lines with larger capacitances have to be driven. Also, the access time may be slower for the external SDRAM than for the internal SRAM.

During display of a frame, power consumption of the graphics functions in the SOC chip is lower during first block 46 than for second block 48 and any subsequent blocks from external SDRAM.

Low-Power Mode Fetches Pixels only from On-Chip Memory—FIG. 8B

FIG. 8B shows a reduced-size display mode that is refreshed with pixels from the on-chip SRAM. The first physical block A begins with the screen start address SSA and is a block in the on-chip SRAM. First block 46 continues until the block end address BEA. The second block B of the frame buffer begins at block start address BSA and continues to the end of the full display. This second block 48 is stored in external SDRAM, which requires more power to access than the on-chip SRAM since external lines with larger capacitances have to be driven.

To save power, the size of the display is reduced to a display window that is a fraction of the normal display. Additional counters and comparators count the number of pixels in the current line, and the line number. When the number of pixels in the current line matches or exceeds the horizontal-active-end HAE value, memory fetching ends for the line. Instead, dummy pixel data is written to the display. The dummy pixels could all be black or gray or some other pre-determined color. These dummy pixels form blank data 82 that is displayed after HAE. Active data 80 contains pixels that are fetched from the on-chip SRAM.

When the current line matches or exceeds the vertical-active end (VAE), memory fetching for the frame ends. Dummy pixels are written to the display, forming blank data 84.

The values for HAE and VAE are set so that the display window of active data 80 falls completely within first block 46, before BEA. Only dummy pixel data occurs in the second block 48, and no pixel-fetches of the external memory are required.

During display of a frame in a stand-by or other low-power mode using only the display window, power consumption of the graphics functions in the SOC chip is lower since only pixels from first block 46 are fetched. No fetches occur for second block 48, so power-hungry fetches from external SDRAM are eliminated.

Active data 80 in the smaller display window can contain status information for the hand-held device, or a smaller amount of information than is available for the full-power mode when the entire display is written. The hand-held device can switch to the standby or low-power display mode when the battery is low, or when little activity is occurring. The device can switch to the higher or full-power mode when the user is actively operating the device and needs more information displayed.

ALTERNATE EMBODIMENTS

Several other embodiments are contemplated by the inventors. For example the address generator of FIG. 5 could be implemented in logic gates and registers, or programmably implemented, or some combination of dedicated hardware and firmware. Other kinds of address translation could be substituted, or paging could be implemented in a variety of ways.

The entire page (all offset address locations within a page) does not have to be used by displayable pixels. Some overhead storage locations may be located on the page, and the last page on a frame can have only some of the available space used. A typical system has many more pages than shown in the drawings. For example, a frame buffer that stores 1 M-byte of pixels uses about 256 physical pages when each page is 4K in length.

The physical address of the memory may be specified in units other than bytes. For example, the physical memory may be read in words of 4 or 8 bytes. The memory address counter can be made to increment by one memory word every other pixel clock, to fetch several pixels at a time. Memory address counter 66 could count downward rather than upward to read blocks from top to bottom.

Some systems may not use vertical and horizontal sync signals, or other timing signals described, or may substitute other signals. Flat-panel and LCD displays may not require sync signals, or may use other signals. However, the invention can be modified to use these substitute signals, or dummy sync signals can be generated. The pixel clock may be stopped while the memory address counter is loaded, or pixel buffering or fast address loading may allow the pixel clock to continue uninterrupted.

The hand-held device can switch to a lower-power mode by changing the color resolution of the display. For example, the display can be switched from a 2 byte per pixel mode to a 2-bit per pixel mode to reduce the frame buffer size and reduce memory fetches. The number of pixels per line, and the numbers of lines per frame may also be changed to reduce power. When the frame buffer size falls below the size of the on-chip SRAM, then a refresh fetches are to the lower-power on-chip memory. Even when some external memory is needed, reducing the overall frame-buffer size reduces the number of external fetches needed and thus reduces power.

The abstract of the disclosure is provided to comply with the rules requiring an abstract, which will allow a searcher to quickly ascertain the subject matter of the technical disclosure of any patent issued from this disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 37 C.F.R. §1.72(b). Any advantages and benefits described may not apply to all embodiments of the invention. When the word “means” is recited in a claim element, Applicant intends for the claim element to fall under 35 USC §112, paragraph 6. Often a label of one or more words precedes the word “means”. The word or words preceding the word “means” is a label intended to ease referencing of claims elements and is not intended to convey a structural limitation. Such means-plus-function claims are intended to cover not only the structures described herein for performing the function and their structural equivalents, but also equivalent structures. For example, although a nail and a screw have different structures, they are equivalent structures since they both perform the function of fastening. Claims that do not use the word means are not intended to fall under 35 USC §112, paragraph 6. Signals are typically electronic signals, but may be optical signals such as can be carried over a fiber optic line.

The foregoing description of the embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. 

1. A multi-block display-refresh controller comprising: a start address selector for selecting a block starting address from a plurality of block starting addresses and a screen starting address, the start address selector being loaded with a series of block starting addresses for a plurality of blocks within a display frame; a selector, coupled to the start address selector, for selecting either the block starting address or a next-line address for output; a line start register, coupled to receive an output of the selector, for storing a line starting address for a horizontal line of pixels in the display frame; a memory address counter that is loaded with the line starting address from the line start register and incremented by a pixel clock as pixels in the horizontal line are written to a display; an adder, receiving the line starting address from the line start register, for adding a line width to the line starting address to generate the next-line address to the selector; a block-end detector, coupled to receive a pixel address from the memory address counter, for detecting a block end when the pixel address matches a block-end address for a current one of the plurality of blocks within the display frame; and wherein the selector selects a new block starting address from the start address selector when the block-end detector detects the block end, but the selector selects the next-line address from the adder when the block end is not detected by the block-end detector, whereby new block starting address are used when block ends are detected as the plurality of blocks of pixels are displayed within a display frame.
 2. The multi-block display-refresh controller of claim 1 wherein when the block end is detected the line start register is loaded from the selector and the memory address counter is loaded from the line start register using a new block starting address from the start address selector, whereby pixel addresses are re-loaded when the block end is detected.
 3. The multi-block display-refresh controller of claim 2 wherein the block end can occur in a middle of a horizontal line of pixels, wherein pixels from two blocks are displayed on a same horizontal line, wherein the two blocks are in non-adjacent memory locations separated by other data.
 4. The multi-block display-refresh controller of claim 3 wherein the block end can also occur at an end of the horizontal line; further comprising: a comparator, receiving the next-line address from the adder, for comparing the next-line address to the block-end address and signaling the block end when the next-line address exceeds the block-end address.
 5. The multi-block display-refresh controller of claim 4 wherein the start address selector is repeatedly over-written with a new block starting address as the series of blocks of pixels in the display frame are read; wherein the block-end address is stored in a block-end register that is repeatedly over-written with a new block-end address for the block that had a block starting address in the start address selector.
 6. A portable system comprising: execute means for executing programs that write pixels for display to a single-block frame buffer; frame-buffer-address translate means, receiving addresses of pixels from the execute means, for translating the addresses of pixels to memory addresses in a plurality of physical memory blocks; low-power memory means for storing some of the plurality of physical memory blocks that store pixels; high-power-memory access means for reading pixels stored in others of the plurality of physical memory blocks that are stored in an external memory; wherein accesses of pixels stored in the external memory consume more power than accesses of pixels stored in the low-power memory means; and display controller means for writing pixels to a display, the display controller means reading pixels stored in the plurality of physical memory blocks including reading pixels stored in the low-power memory means and pixels stored in the external memory; wherein the display controller means further comprises: pixel counter means, having a pixel address that is incremented in response to a pixel clock as pixels are read from the lower-power memory means or from the external memory; block-end register means for storing a block-end address of a current block in the plurality of physical memory blocks; block-start register means for storing a block-start address of the current block in the plurality of physical memory blocks; block-end detect means for detecting a block end when the pixel address from the pixel counter means reaches the block-end address from the block-end register means; select means for loading the pixel counter means with a next block-start address from the block-start register means when the block-end detect means detects the block end, ; line start register means, loaded by the select means with the next block-start address when the block end is detected, for storing a starting pixel address for a display line; and add means, receiving the starting pixel address from the line start register means, for adding a line-width of pixels to generate a next-line starting pixel address to be loaded into the line start register means at an end of the display line; whereby pixels in the single-block frame buffer are stored in multiple physical blocks in both the low-power memory means and in the external memory and whereby the pixel counter means is re-loaded with the next block-start address when the block end is detected.
 7. The portable system of claim 6 wherein the low-power memory means is a memory on a same substrate as the execute means and the display controller means, but the external memory is on a separate substrate.
 8. The portable system of claim 6 wherein the display controller means can enter a low-power mode wherein pixels are fetched only from the low-power memory means but not from the external memory, the display controller means can also enter a high-power mode wherein pixels are fetched from both the low-power memory means and from the external memory; wherein the high-power mode consumes more power that the low-power mode.
 9. The portable system of claim 6 further comprising: window means, in the display controller means, for detecting when a current location for pixel fetching reaches a window limit, the window means preventing memory accesses to fetch pixels after the window limit is reached but instead supplying a fixed pixel for display, whereby fixed pixels rather than memory-fetched pixels are displayed once the window limit is reached.
 10. An apparatus for generating memory addresses corresponding to locations within a frame buffer, wherein said memory addresses are located in one or more memory blocks, said apparatus comprising: a memory address generation unit configured to receive a starting address of a current memory block corresponding to said frame buffer, and wherein said memory address generation unit is further configured to generate pixel addresses corresponding to one or more pixels within said current memory block; a block end detection unit configured to determine whether a current pixel address generated by said memory address generation unit matches an end address for said current memory block, wherein said memory address generation unit is further configured to receive a starting address of a next memory block corresponding to said frame buffer in response to said block end detection unit determining said current pixel address matches said end address for said current memory block, wherein said end address of said current memory block corresponds to a given pixel location within a given display line of said buffer, and wherein said given pixel location corresponds to a location other than an end of said given display line.
 11. The apparatus of claim 10, wherein said current memory block is located on a different physical substrate from said next memory block.
 12. The apparatus of claim 11, wherein said apparatus is configured to operate in a reduced power mode when all of said one or more memory blocks corresponding to said frame buffer are located in a single physical device.
 13. An apparatus for fetching pixels from a frame buffer, said frame buffer including at least a first memory block and a second memory block, said apparatus comprising: an address generator configured to receive a starting address of said first memory block, wherein said address generator is configured to generate addresses usable for fetching pixels from said first memory block; a block end detector configured to determine whether an address generated by said address generator corresponding to said first memory block matches an end address of said first memory block; wherein said address generator, in response to said block end detector determining that said address generated by said address generator matches the end address of said first memory block, is configured to receive a starting address of said second memory block and to generate addresses usable for fetching pixels from said second memory block; wherein said end address of said first memory block corresponds to a given pixel location within a given display line of said buffer, and wherein said given pixel location corresponds to a location other than an end of said given display line.
 14. The apparatus of claim 13, wherein said first memory block is located on a different physical device from said second memory block.
 15. The apparatus of claim 13 wherein said apparatus is configured to operate in a first power mode in which all of said memory blocks included in said frame buffer are located on a same substrate, and wherein said apparatus is configured to operate in a second power mode in which said first memory block and said second memory block are located on different substrates, and wherein said apparatus is configured to consume more power in said second power mode than in said first power mode.
 16. A system, comprising: a central processing unit (CPU) configured to execute programs; a frame buffer configured to store pixel values wherein physical addresses corresponding to said frame buffer include at least a first memory block and a second memory block; and a display controller configured to read pixel values from said frame buffer and write said pixel values to a display; wherein said display controller includes: an address generator configured to receive a starting address of said first memory block, wherein said address generator is configured to generate addresses usable for fetching pixels from said first memory block; and a block end detector configured to determine whether an address generated by said address generator matches an end address of said first memory block; wherein said address generator, in response to said block end detector determining that said address generated by said address generator matches the end address of said first memory block, is configured to receive a starting address of said second memory block and to generate addresses usable for fetching pixels from said second memory block, wherein said end address of said first memory block corresponds to a given pixel location within a given display line of said frame buffer, and wherein said given pixel location corresponds to a location other than an end of said given display line.
 17. The system of claim 16, further comprising a memory management unit (MMU) configured to receive virtual addresses from said CPU and to translate said received virtual addresses into physical addresses, wherein said frame buffer corresponds to a contiguous group of virtual addresses and one or more physical blocks of memory, including said first memory block and said second memory block.
 18. The system of claim 17, wherein said first memory block is located in a different physical device from said second memory block.
 19. The system of claim 18, wherein said CPU, said MMU, and said display controller are located on a same physical device as said first memory block.
 20. The system of claim 17, wherein said system is configured to operate in a first power mode in which all of said memory blocks included in said frame buffer are located on a same substrate, and wherein said system is configured to operate in a second power mode in which said first memory block and said second memory block are located on a different substrate, wherein said apparatus is configured to consume more power in said second power mode than in said first power mode.
 21. A method comprising: receiving a starting address of a current memory block corresponding to a frame buffer; generating pixel addresses corresponding to one or more pixels within said current memory block; determining that a pixel address generated by said memory address generation unit matches an end address for said current memory block; receiving a second starting address of a next memory block corresponding to said frame buffer in response to said determining said current pixel address matches said end address for said current memory block, wherein said end address of said current memory block corresponds to a given pixel location within a given display line of said frame buffer, and wherein said given pixel location corresponds to a location other than an end of said given display line.
 22. The method of claim 21, wherein said current memory block is located on a different physical substrate from said next memory block. 